FullSFPack allows to use standard dialogs for seleting a file, folder or volume. It allows even to deal with Alias files themselves rather than with pointed entries, and adds a multiple files selection dialog.
<G[et]|P[ut]|V[olume]|F[older]|M[ultiple]|Q[uickTime]> is the action param and defines the desired dialog.
<type 1[…,type 4]> is a 1 to 4 items list containing types of files to display in the dialog. Default presents all files.
<default dir> is a full pathname string allowing to set the current directory when the dialog pops on screen.
<new name> is a string only needed with "P[ut]", and gives the default name for the new file in the dialog's edit field.
<prompt> is the message string appearing in the dialog.
"dontResolveAlias" allows to get the alias file pathName rather than those from the pointed file. Applies only to G[et] and M[ultiple].
Using "!", "?" or "=" as first parameter will return an online help (resp.
USING
------
FullSFPack requires System 7.0.
The XFCN returns the full patname of the selected file, folder or volume.
With "M[ultiple]", it returns a return delimited list of all collected files.
With "P[ut]", you can know if the user wants to replace an existing file by testing FullSFPackReplacing global variable wich may contain "true" or
"false".
Q[uickTime] option require QuickTime to be installed, and allows viewing and on-the-fly creation of PICT and MooV file previews.
FullSFPack doesn't need any associated DLOG/DITL resources, and is able to create them on the fly when needed.
MeanWhile, when called from a stack on a locked volume, the XFCN isn't able to add those new resources to the current stack. That's why resources have been provided in this stack, and the XFCN detects their availability.
Finally, on locked volume, if you forgot to copy these needed DLOG/DITL resources, FullSFPack still tries to work by using standard resources from the System (except for M[ultiple] and F[older] which always need custom dialog). Only difference : there will be no prompt displayed.
Depending on requested action, you will need to add the following resources (don't rename them !) :
This (these) external(s) is (are) FreeWare,allowing unlimited use in any non-commercial stack. You just need in this case to mention the author's name and copyright in your stack.
Any commercial use must be licensed and aknowledged by the author.